Sourced from rules_python's releases.

2.1.0-rc0

For more detailed setup instructions, see https://rules-python.readthedocs.io/en/latest/getting-started.html

For the user-facing changelog see here

Using Bzlmod

Add to your MODULE.bazel file:

bazel_dep(name = "rules_python", version = "2.1.0-rc0")
python = use_extension("@​rules_python//python/extensions:python.bzl", "python")
python.toolchain(
python_version = "3.13",
)
pip = use_extension("@​rules_python//python/extensions:pip.bzl", "pip")
pip.parse(
hub_name = "pypi",
python_version = "3.13",
requirements_lock = "//:requirements_lock.txt",
)
use_repo(pip, "pypi")

Using WORKSPACE

Paste this snippet into your WORKSPACE file:

load("@bazel_tools//tools/build_defs/repo:http.bzl", "http_archive")
http_archive(
name = "rules_python",
sha256 = "8c8c28f9fc1cc8fd2a24df47deb9da8dc0d5567fa5ab48085515fa92c8cb56d0",
strip_prefix = "rules_python-2.1.0-rc0",
url = "https://github.com/bazel-contrib/rules_python/releases/download/2.1.0-rc0/rules_python-2.1.0-rc0.tar.gz",
)
load("@​rules_python//python:repositories.bzl", "py_repositories")
py_repositories()

Gazelle plugin

Paste this snippet into your WORKSPACE file:

... (truncated)

Sourced from rules_python's changelog.

:::{default-domain} bzl :::

rules_python Changelog

This is a human-friendly changelog in a keepachangelog.com style format. Because this changelog is for end-user consumption of meaningful changes, only a summary of a release's changes is described. This means every commit is not necessarily mentioned, and internal refactors or code cleanups are omitted unless they're particularly notable.

A brief description of the categories of changes:

• Changed: Some behavior changed. If the change is expected to break a public API or supported behavior, it will be marked as BREAKING. Note that beta APIs will not have breaking API changes called out.
• Fixed: A bug, or otherwise incorrect behavior, was fixed.
• Added: A new feature, API, or behavior was added in a backwards compatible manner.
• Particular sub-systems are identified using parentheses, e.g. (bzlmod) or (docs).

{#v2-1-0}

... (truncated)

• 5c32fa9 chore: prepare 2.1 release (#3829)
• 102b501 feat: expose interpreter files-to-run on PyRuntimeInfo (#3795)
• 6ce7840 fix(coverage): handle nested coverage collection (#3823)
• 44ec76f docs: update changelog for 2.0.3 release (#3820)
• 99d0c3d refactor(toolchains): register runtimes using manifest (#3812)
• 7053e26 Gazelle: Delete stale py_library and py_test targets (#3817)
• 42c8e75 feat(toolchains): support runtime registration from manifest (#3802)
• c0fef46 fix(uv): respect uv.tool settings in pyproject.toml (#3811)
• 8b38325 build: configure secondary mirror fallback (#3814)
• dcb7dfa feat: add //command_line_option:extra_toolchains pseudo-flag (#3810)
• Additional commits viewable in compare view

You can trigger Dependabot actions by commenting on this PR:

• @dependabot rebase will rebase this PR
• @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
• @dependabot show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
• @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)